Hello, @julien-leclercq! This is your first Pull Request that will be reviewed by Ebert, an automatic Code Review service. It will leave comments on this diff with potential issues and style violations found in the code as you push new commits. You can also see all the issues found on this Pull Request on its review page. Please check our documentation for more information.

@julien-leclercq Nice try :). But updating Ecto like that doesn't work for adapters, there were some breaking changes in query planning so to update adapter to the latest Ecto we will need to put more work into it.

Here is PR that explains what was changed: elixir-ecto/ecto#2155

haha thanks for the quick answer and the welcoming message. Have you tried to implement it ? Does it look like a complicated task for someone just getting on board on this project ?

Do we want to remain backward compatible ?

@julien-leclercq we should keep backwards compatibility (the PR above explains how we can archive it). I've spent about an hour looking how to update Ecto, it should be relatively easy but eventually decided to wait for Ecto 3.0 to adapt to all the changes in one hop.

If you have time to work on it, I would be super-happy to help you along the way 👍.

sorry, I tried to look at it but I think my ecto knowledge is to thin at the moment for me to help, I am struggling understand what is to be changed. :(

No worries. I think @beardedeagle already works on this one, so we may see support pretty soon. Anyways I'll support Ecto 3.0 when it's out.

would you have advice on where to start to dive in ecto mecanisms understanding ?

@julien-leclercq it depends on what goals do you have, if you just want to learn how to use it - better build some apps with it. If you want to know internals - try contributing and make an adapter (contribution is easier because there is a lot of maintainers that would guide you).